home *** CD-ROM | disk | FTP | other *** search
- Path: nwestnews.nwest.mccaw.com!usenet
- From: jeffrey.rhodes@attws.com
- Newsgroups: psi.interramp.isdn,comp.dcom.modems,comp.dcom.isdn
- Subject: Re: Anyone getting 64 kbps w/ BSP per channel with *ASYNCHRONOUS* com port?
- Date: Thu, 14 Mar 96 16:50:17 PDT
- Organization: AT&T Wireless Services, Inc.
- Message-ID: <NEWTNews.826851552.30207.jrhodes@jrhodespc.nwest.mccaw.com>
- References: <4i47m9$21u@usenet4.interramp.com> <161@dynasoft_.win.net>
- NNTP-Posting-Host: jrhodespc.nwest.mccaw.com
- Mime-Version: 1.0
- Content-Type: TEXT/PLAIN; charset=US-ASCII
- X-Newsreader: NEWTNews & Chameleon -- TCP/IP for MS Windows from NetManage
-
-
- In article <161@dynasoft_.win.net>, <hrwillet@dynasoft_.win.net> writes:
- >
- > 57 is async mode
- > 64 is sycn mode
- >
- >
- > In article <4i47m9$21u@usenet4.interramp.com>, Daveros@interramp.com
- (Daveros@interramp.com) writes:
- > >Is there anyway or anyone who knows about getting 64 kbps per single
- > >channel instead of 57.6 kbps? The books I've been reading say that 115.2
- > >kbps is the max for 2 channels bonded, and I understand that, but they
- > >also say that for single channel (asynchronous) you can only get half
- > >that...57.6. Why can't I get 64?
- > >
- > >
- >
- > ---
- > Herman R. Willett
-
- Good answer. The interesting thing is if you set up a sync1 or sync2 BSP
- connection and request "clear channel, no protocol" to an answering BSP
- similarly configured, and if then you run an async protocol like ZMODEM
- for file transfer, you will discover that the async protocol running
- under the sync clear channel connection can only support 19,200. When you
- bump the async speed to 38,400 ZMODEM starts having problems and at
- 57,600 the connection is useless. No doubt this has something to do with
- the BSP's buffer management at the async to sync border.
-
- I think this is the reason the BSP's terminal program is limited to 19,200.
-
-
- Jeffrey Rhodes at jeffrey.rhodes@attws.com
-
-
-
-